Skip to content
This repository was archived by the owner on May 24, 2026. It is now read-only.

Fix schema validator to support published manifest metadata#40

Merged
GsCommand merged 1 commit into
mainfrom
codex/fix-failing-github-check-for-pr-#39
Apr 28, 2026
Merged

Fix schema validator to support published manifest metadata#40
GsCommand merged 1 commit into
mainfrom
codex/fix-failing-github-check-for-pr-#39

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • The CI schema validation failed because manifest.json is in "publication_state": "published" with a non-null release_date, while the validator only allowed pre-publication metadata; the validator needs to be state-aware so published manifests validate correctly.

Description

  • Updated scripts/validate-all.mjs to allow publication_state to be either repository-validated-not-yet-published or published and to enforce release_date === null for the former and an ISO YYYY-MM-DD string for the latter; also updated CHANGELOG.md to document the validator change.

Testing

  • Ran npm ci and npm run validate (the run initially failed on the manifest assertion before the fix) and after the change ran npm test and npm run validate:schemas, all of which passed.

Codex Task

@GsCommand GsCommand merged commit a818452 into main Apr 28, 2026
1 check passed
@GsCommand GsCommand deleted the codex/fix-failing-github-check-for-pr-#39 branch May 24, 2026 22:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant